Task: Create Item definition
Capture information relevant to the item such as to support an adequate understanding of the items intended behavior.
Purpose

Provides an initial set of requirements from which the system must be developed.

Relationships
RolesPrimary: Additional: Assisting:
InputsMandatory: Optional:
  • None
External:
  • None
Outputs
Main Description

The requirements to be captured cover a number of areas such as;-

Functional, non-functional and legal requirements, as well as the dependencies between the item and its environment.

Safety requirements that are already known about, these cover behavior achieved by similar functions, assumptions on behavior expected by the item and potential consequences of behavior shortfalls, including failures modes and hazards.

This task could be considered to be similar to capturing stakeholder requirements.

The scope of item development and interfaces also needs to be understood, this is determined by considering interactions with items or elements outside the scope of the system, allocation and distribution of functions to architecture and operating scenarios, if they impact the functionality of the item.

This can be achieved using Use Case modeling if an MBSE approach is being used, see SE Overview. This details a generic process for developing systems using model based techniques and gives an overview of the process. The user is recommended to examine Elaborate Draft System Requirements Specification, in particular, to help with the item definition.

For a more detailed understanding of the requirements for Item Definition the user is referred to ISO 26262 vol 3 clause 5.

Steps
Determine the scope of item and relationships to other systems

The intent of this task is to determine the boundary of the item under development, this sets the context for its interfaces and its interactions with its peer systems and their requirements, which constrain the item under development.


Capture the items requirements
The items requirements come in a number of different forms, functional (behavioral), non functional (performance, environmental or quality of service related) or legal (laws, national or international standards). The objective of this task is to capture and identify these requirements.
Capture already know safety requirements
The objective of this task is to capture the behavior of the item, any assumptions on the expected behavior of the item and understand the possible consequences if the behavior does not meet its expectations. This should also cover any know hazards and failure modes.
Properties
Predecessor
Multiple Occurrences
Event Driven
Ongoing
Optional
PlannedYes
Repeatable
Key Considerations

Practices applicable to help create the item definition